Release 10.1A: OpenEdge Getting Started:
WebSpeed Essentials

Deployment configuration with a dedicated Web server

When you deploy your applications, you do not need all the components that usually exist in a development configuration.

Figure 4–5 shows the products installed in a deployment network with a dedicated Web server.

Note: The WebSpeed Broker and the WebSpeed Agents it controls are collectively referred to as the WebSpeed Transaction Server in this figure.

Figure 4–5: Deployment configuration with a dedicated Web server

This configuration has the WebSpeed Messenger product installed on the Web server’s machine, Oberon. The main machine, Uranus, has the WebSpeed Enterprise Transaction Server and some data source. The end users only need a Web browser to link up to your applications. They do not need any OpenEdge product installed on their machines.

To set up a deployment network with a dedicated Web server:

Install a Web server on Oberon.
Install the WebSpeed Messenger on Oberon.
Note: Since the WebSpeed WebTools are only meant for developers, you should remove access to them. During the Messenger-only installation, do not choose the option to either create a virtual directory or copy the static HTML files.
Install the WebSpeed Enterprise Transaction Server on Uranus.
Install the appropriate components for your intended data source on Uranus:
If you use the OpenEdge Database, install the OpenEdge Enterprise RDBMS.
If you connect to a non-OpenEdge data source, install the appropriate OpenEdge DataServers for your data source. See the appropriate OpenEdge DataServer guide for details.
Install your r-code on Uranus and include its location in the WebSpeed agent’s PROPATH.
Copy any Java applet, static HTML, and .gif files needed for your applications to the Web server’s /docroot/webspeed directory on Oberon.

Beyond the basic installation

As described, this configuration uses the components for a heavy load system. If you expect a light load on the network, you might consider installing the WebSpeed Transaction Server and Workgroup RDBMS instead of the Enterprise Transaction Server and Enterprise RDBMS. The WebSpeed Transaction Server can handle up to 50 WebSpeed Agents. The Workgroup RDBMS can handle up to 65 connections.

When you expect heavy loads on your network or want to increase its fault tolerance, you might want to add the load balancing option for the NameServer. If you deploy several WebSpeed Transaction Servers that support the same application service, you can use load balancing to control how the load is spread over them. See the "Understanding the NameServer’s load balancing option" section.

If you are going to use a non-OpenEdge database, you must install the appropriate DataServer on the Uranus server.

Startup sequence

After you have installed and configured everything, you can start your WebSpeed environment.

To start a deployment network with a dedicated Web server:

Start the AdminServer on Uranus.
Note: Once the AdminServer has started, you can use the Progress Explorer to start other components on Uranus.
Start the data source (and the data server broker, if needed) on Uranus in multi-user mode.
Start the NameServer on Uranus.
Start the WebSpeed Transaction Server on Uranus.
Start the Web server on Oberon.